Wireless account management application for a wireless device

ABSTRACT

A method for displaying wireless service usage information and account information using an account management application operating on a wireless device includes receiving, at the account management application operating on the wireless device and from a tracking module, wireless service usage information for a wireless subscriber associated with the wireless device, the wireless service usage information including one or more units of wireless services that the wireless subscriber has used, receiving, at the account management application operating on the wireless device and from a service provider over a wireless network, account information associated with the wireless subscriber associated with the wireless device, the service provider being different from the wireless device and the wireless network, and enabling presentation, on a display of the wireless device, of the account management application including the wireless service usage information and the account information for the wireless subscriber associated with the wireless device.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.15/156,881 filed May 17, 2016, now U.S. Pat. No. 10,158,763 issued onDec. 18, 2018; which is a continuation U.S. patent application Ser. No.14/218,266 filed Mar. 18, 2014, now U.S. Pat. No. 9,344,583 issued onMay 17, 2016, which claims the benefit from U.S. Provisional ApplicationNo. 61/786,804 filed on Mar. 15, 2013, which are all hereby incorporatedby reference in their entirety for all purposes as if fully set forthherein.

TECHNICAL FIELD

The following disclosure generally relates to managing a subscriber'swireless account using an application for a wireless device and, moreparticularly, relates to tracking usage and enabling purchase of variouswireless services using an application installed on the wireless device.

BACKGROUND

Wireless services, such as cellular or mobile phone services, typicallyinclude voice services, Short Message Service (“SMS”) services, and dataservices. A wireless service provider typically bundles a particularnumber of voice minutes, a particular number of SMS messages, and anamount of data transfer for a prepaid or postpaid monthly wireless plan.A subscriber may purchase a bundle appropriate for his/her usage. Whenthe subscriber places or receives a call, sends or receives an SMSmessage, and/or uploads or downloads data from his/her wireless device,appropriate units of usage are deducted from the subscriber's monthlywireless plan.

To initially purchase a bundle of wireless services, a subscribertypically visits a physical location, calls customer support, and/orvisits a website operated by the wireless service provider or a thirdparty. The subscriber then selects a bundle of usage appropriate forhis/her needs. The amount of usage is credited to the subscriber'saccount and the wireless service is made available for use by thesubscriber. In order to purchase additional usage or change his/hermonthly wireless plan, the subscriber can again visit the physicallocation, call customer support, and/or visit a website operated by thewireless service provider or third party. However, visiting a physicallocation or calling customer support to purchase additional usage istime consuming for the subscriber and not available at any time. Using awebsite to purchase additional usage requires that the subscriberrecalls or searches for the address of the website and navigates througha series of webpages.

Currently, many wireless devices use applications specific to theoperating system of the wireless device to perform a multitude of tasks,such as playing games, editing documents, checking email, and purchasinggoods and/or services. Such applications are readily accessible on homepages of the wireless devices and enable a user of the wireless deviceto quickly perform popular functionalities. For example, the user canquickly purchase a good and/or service of interest by using a particularmerchant's mobile application.

Therefore, to improve a wireless subscriber's experience in tracking andpurchasing wireless services, a new wireless account managementapplication for a wireless device is needed.

SUMMARY

In one aspect a method for displaying wireless service usage informationand account information using an account management applicationoperating on a wireless device includes receiving, at the accountmanagement application operating on the wireless device and from atracking module locally stored on the wireless device, wireless serviceusage information for a wireless subscriber associated with the wirelessdevice, the wireless service usage information including one or moreunits of wireless services that the wireless subscriber has used,receiving, at the account management application operating on thewireless device and from a service provider over a wireless network,account information associated with the wireless subscriber associatedwith the wireless device, the service provider being different from thewireless device and the wireless network, and enabling presentation, ona display of the wireless device, of the account management applicationincluding the wireless service usage information and the accountinformation for the wireless subscriber associated with the wirelessdevice.

Details of one or more implementations of a wireless account managementapplication for a wireless device are set forth in the accompanyingdrawings and the description below. Other aspects of the wirelessaccount management application for a wireless device will be apparentfrom the description and drawings, and from the claims.

DESCRIPTION OF DRAWINGS

FIG. 1 illustrates a block diagram of an exemplary wireless device.

FIG. 2 illustrates an exemplary wireless device.

FIG. 3 illustrates a schematic diagram showing the connectivity betweena wireless device, a plurality of mobile network operators, and a mobilevirtual network operator.

FIG. 4 illustrates an exemplary account information database structure.

FIGS. 5a, 5b, 5c, and 5d illustrate exemplary graphical user interfacesof a wireless account management application.

FIG. 6 illustrates a flowchart showing an exemplary process fordisplaying wireless service usage information and account information ona wireless device.

Like reference symbols indicate like elements throughout thespecification and drawings.

DETAILED DESCRIPTION

FIG. 1 illustrates a block diagram of an exemplary wireless device. Thewireless device 10 can be any mobile technology computing device thatconnects to a wireless communication network such as, for example, amobile phone, a wireless handset, a wireless dongle, user equipment, amobile station, or the like. The wireless device 10 includes a display12, an input device 14, a transceiver 16, a processor 18, a memory 20,and may include a Universal Integrated Circuit Card (“UICC”) orSubscriber Identity Module (“SIM”) card 22. In some implementations, theSIM card 22 can be removably received within a card slot (not shown) inthe wireless device 10 and can include internal SIM memory 24. The SIMcard 22 can store identification information such as an InternationalMobile Subscriber Identity (“IMSI”), a key used to identify andauthenticate subscribers using the wireless device 10, or the like. TheSIM card 22 can be configured to be transferred between differentwireless devices 10. In other implementations, the wireless device 10can operate without a UICC or SIM card 22.

The processor 18 is capable of processing instructions for executionwithin the wireless device 10. For example, the processor 18 can processinstructions stored in the memory 20 to display graphical information onthe display 12 and/or to transmit or receive data using the transceiver16. In some implementations, the processor 18 can process applicationinstructions to display a wireless account management application on thedisplay 12. The processor 18 can be a single-threaded processor or amulti-threaded processor. The memory 20 can include, for example,volatile or non-volatile random access memory (“RAM”) and/or read onlymemory (“ROM”). The components 12, 14, 16, 18, and 20 within thewireless device 10 communicate through an internal bus 26.

FIG. 2 illustrates an exemplary wireless device. The wireless device 10may include a display 12 that is a screen that can be touch sensitive.The input device 14 can include one or more of a keypad 28, a trackball30, selectable buttons 32, a touch screen 34 having selectable regions,or the like. The wireless device 10 may also include an antenna (notshown) coupled to the transceiver 16 to facilitate the transmission andreceipt of communications by the wireless device 10.

FIG. 3 illustrates a schematic diagram showing the connectivity betweena wireless device 10, a plurality of mobile network operators (“MNO”)networks 302 and 304, and a mobile virtual network operator (“MVNO”)cloud 306. The MVNO cloud 306 includes a tracking module 308 and awireless subscriber service system 320 that includes an accountinformation database 322. The wireless device 10 includes a trackingmodule 310 and a wireless account management application 312.

Although two MNO networks 302 and 304 are illustrated in FIG. 3, anynumber of MNO networks can be available. The wireless device 10 mayconnect to one of the MNO networks 302 and 304 depending on thegeographic location of the wireless device 10, the availability of theMNO networks 302 and 304, and/or the service contract associated withthe wireless device 10. The MNO networks 302 and 304 can be any type ofwireless network, such as a cellular data network, e.g., a Global Systemfor Mobile Communication (“GSM”) network, a Code-Division MultipleAccess (“CDMA”) network, a Universal Mobile Telecommunications System(“UMTS”) network, an Evolution-Data Optimized (“EV-DO”) network, a LTEnetwork, a wireless local network, a wide area network, or the like.

In some implementations, a wireless subscriber purchases a wirelesscommunications plan from a MVNO. The MVNO is a wireless operator thattypically does not own its own frequency spectrum or have its ownnetwork infrastructure. Instead, MVNOs contract for the right to accessa wireless communications network owned by a MNO and sell that access totheir wireless subscribers. Therefore, to provide activation, metering,additional services, and other customer services to their subscribers,MVNOs operate systems, such as the MVNO cloud 306, that communicate withthe MNO networks 302 and 304.

The MVNO cloud 306 communicates with the MNO networks 302 and 304 toreceive information about the usage of the wireless device 10 on the MNOnetworks 302 and 304. The MVNO cloud 306 can be one or more of dedicatedhardware, application specific integrated circuits, programmable logicarrays, computers, and servers including one or more processors and oneor more memories. For example, the one or more processors of the MVNOcloud 306 can be configured to perform the functions of the trackingmodule 308 and the wireless subscriber service system 320 and the one ormore memories of the MVNO cloud 306 can be configured to store the usageinformation in the tracking module 308 and the account information ofthe wireless subscribers of the MVNO in an account information database322.

The tracking module 308 can store the usage information for each of thesubscribers of the MVNO from the start of a relationship between thewireless subscriber and the MVNO and for predefined time periods. Forexample, the usage information can be stored in one month increments. Insome implementations, to avoid compromising the integrity of the usageinformation and the account information, the information stored on thetracking module 308 and the wireless subscriber service system 320 canbe stored in a secure memory of the MVNO cloud 306 and/or encrypted.

The wireless subscriber service system 320 can be implemented as one ormore of software or hardware. The wireless subscriber service system 320manages the services provided by the MVNO to the wireless subscribers.In some implementations, the wireless subscriber service system 320provides and/or enables the functions of the wireless account managementapplication 312. The wireless subscriber service system 320 can alsoprovide one or more of advertisements, self-care, diagnostics, alertmanagement, policy control, payment handling, offer management, campaignmanagement, analytics, reporting, and data ratings.

For example, the wireless subscriber service system 320 can select theadvertisements to be presented to the wireless subscriber using thewireless account management application 312 based on the subscriber'saccount information. In particular, if the subscriber has a low numberof voice minutes, i.e., lower than a predetermined number of voiceminutes, remaining in his/her wireless account, the wireless subscriberservice system 320 can select an advertisement for the purchase ofadditional voice minutes. In some implementations, if the subscriber hasa low number of voice minutes, i.e., lower than a predetermined numberof voice minutes, remaining in his/her wireless account, the wirelesssubscriber service system 320 can enable the purchase of additionalminutes of voice usage and/or automatically apply reserved voice minutesto the subscriber's account. In another example, if the MVNO is runninga campaign to sell SMS messaging service at a discount for the month ofJanuary, the wireless subscriber service system 320 can select anadvertisement for the purchase of the discounted SMS messages. In yetanother example, the wireless subscriber service system 320 can sendwireless service purchase information to the wireless account managementapplication 312 for selection by the wireless subscriber.

The account information database 322 in the wireless subscriber servicesystem 320 stores the account information associated with each of thewireless subscribers of the MVNO. The account information can includethe identification and contact details of the wireless subscribers, thedetails of a transaction performed at the wireless account managementapplication 312, and the history of transactions between the wirelesssubscriber and the MVNO, including wireless device 10 identifiers,transaction identifiers, vendor identifiers, and billing information, asexplained in greater detail with regard to FIG. 4.

To track the usage of the wireless device 10, tracking modules 308 and310 are used. In some implementations, the tracking module 308 can beincluded in the MVNO cloud 306 or the tracking module 310 can beincluded in the wireless device 10. For example, tracking module 310 cantrack usage of the wireless device 10 and tracking module 308 can trackusage for all wireless devices associated with the MVNO. In yet otherimplementations, the tracking modules 308 and 310 can be located in boththe MVNO cloud 306 and the wireless device 10. For example, the trackingmodules 308 and 310 can store the usage of various wireless services,such as minutes of voice calls, number of SMS messages, and/or amount ofdata transferred. The usage information can be sent between the trackingmodules 308 and 310 through one or more of the MNO networks 302 and 304.

The tracking modules 308 and 310 can be implemented as one or more ofsoftware or hardware. The tracking modules 308 and 310 can coordinateone or more of provisioning, metering, accumulating, and consolidatingwireless service usage for the wireless subscribers.

The tracking module 310 included in the wireless device 10 may bepre-installed or post-installed on the wireless device 10 and can beupdated over time using Over The Air (“OTA”) programming or non-OTAprogramming. The tracking module 310 may be stored or executed on, forexample, the memory 20, the UICC/SIM memory 24, dedicated hardware,application specific integrated circuits, programmable logic arrays,and/or the processor 18 of the wireless device 10. The instructions forthe tracking module 310 may be included in hardware of the wirelessdevice 10 or in an application stored in the memory 20 and/or the SIMmemory 24 of the wireless device 10 and run by the operating system ofthe wireless device 10. The processes, features, and/or functions of thetracking module 310 may be performed with or without human interactionor augmentation.

The tracking modules 308 and 310 can store the usage of various wirelessservices such as, for example, the number of voice calls, the number offree voice minutes used, the number of metered voice minutes used, thetotal number of voice minutes used, the number of free SMS messages sentand/or received, the number of metered SMS messages sent and/orreceived, the total number of SMS messages sent and/or received, thefree amount of data uploaded and/or downloaded, the metered amount ofdata uploaded and/or downloaded, and the total amount of data uploadedand/or downloaded. Other types of wireless services are contemplated aswell.

The usage statistics can be stored from the start of a relationshipbetween the wireless subscriber and the MVNO and for predefined timeperiods. For example, the usage statistics can be stored in one monthincrements. The tracking module 310 can forward the usage information tothe tracking module 308 of the MVNO cloud 306 through the MNO networks302 and 304 at predetermined time intervals, in response to a request bythe MVNO cloud 306, in response to a triggering event, or the like. Forexample, the usage information can be forwarded to the MVNO cloud 306every three hours, once a day, once a week, in response to movement ofthe wireless device 10 from a predefined geographic area, in response toeach usage of a wireless service, in response to a predefined amount ofusage of one or more wireless services, in response to every startup ofthe wireless device 10, or the like.

The tracking modules 308 and 310 also identify the wireless device 10and/or the particular wireless subscriber using the wireless device 10by providing identification information of the wireless device 10 and/orthe wireless subscriber. For example, the identification information caninclude an identification number for the wireless subscriber or anidentification number for the SIM card 22 associated with the wirelesssubscriber, such as an Integrated Circuit Card Identification (“ICCID”),Electronic Serial Number (“ESN”), International Mobile EquipmentIdentity (“IMEI”), International Mobile Subscriber Identity (“IMSI”),Local Area Identity (“LAI”), or the like. The identification informationcan be specific to allow the MVNO to identify the wireless device 10and/or wireless subscriber.

In some implementations, to avoid compromising the integrity of theidentification information and the usage information, the informationstored on the tracking module 310 can be stored in a secure memory ofthe wireless device 10 and/or encrypted. The identification and usageinformation can be provided to the tracking module 308 of the MVNO cloud306 in encrypted form and/or according to a specific network protocol.

The wireless device 10 also includes a wireless account managementapplication 312. The wireless account management application 312 is asoftware application that enables management of a subscriber's accountwith the MVNO using the wireless device 10. For example, the subscribercan view usage of wireless services, change his/her wirelesscommunications plan from the MVNO, purchase additional usage of wirelessservices from the MVNO, access other applications for download and/orpurchase, purchase and/or receive information on international wirelessservices, receive customer service including real-time troubleshootingservices, find retailers, receive information on promotions from theMVNO, receive advertisements from the MVNO, and the like, using thewireless account management application 312, as explained in greaterdetail with regard to FIGS. 5a -d.

The wireless account management application 312 included in the wirelessdevice 10 may be pre-installed or post-installed on the wireless device10 and can be updated over time using Over The Air (“OTA”) programmingor non-OTA programming. For example, the wireless subscriber using thewireless device 10 can choose to install the wireless account managementapplication 312 on the wireless device 10 at any time. The wirelessaccount management application 312 may be stored or executed on, forexample, the memory 20, the UICC/SIM memory 24, dedicated hardware,application specific integrated circuits, programmable logic arrays,and/or the processor 18 of the wireless device 10. The wireless accountmanagement application 312 may be specific to and run by the operatingsystem of the wireless device 10.

The wireless account management application 312 can receive usageinformation from the tracking module 310 included in the wireless device10 and/or from the tracking module 308 included in MVNO cloud 306. Thewireless account management application 312 can receive accountinformation for the subscriber from the wireless subscriber servicesystem 320 including the account information database 322 of the MVNOcloud 306. For example, the wireless account management application 312can receive all usage information from the tracking module 310 includedin the wireless device 10 and account information from the wirelesssubscriber service system 320 of the MVNO cloud 306. In another example,the wireless account management application 312 can receive some usageinformation from the tracking module 310 included in the wireless device10, other usage information from the tracking module 308 included inMVNO cloud 306, and account information from the wireless subscriberservice system 320 of the MVNO cloud 306.

FIG. 4 illustrates an exemplary account information database structure400. The account information database structure 400 includes a data typefield 402 and a data field 404. Although one data field 404 isillustrated in FIG. 4 corresponding to a single transaction, any numberof data fields can be stored in the account information databasestructure 400 depending on the number of transactions made by thesubscribers of the MVNO. In some implementations, the data field 404 canstore information regarding a transaction by the subscriber using thewireless account management application 312. However, some or the entiredata field 404 can also store information regarding a transaction by thesubscriber at a physical location, by calling customer service, using awebsite, or the like. As such, all of the transactions by thesubscriber, regardless of the means that the transactions were made, canbe stored in a single database.

One or more of the entries 406-450 can be stored in the service accountinformation database structure 400. Entries 406-412 identify thewireless device 10 used to make a transaction. Entry 406 stores theserial number of the wireless device 10 used to make the transaction,such as “XYZ123456.” The serial number of the wireless device 10 can bea serial number assigned to the device by its manufacturer or can be theICCID and/or ESN. Entry 408 stores the brand of the wireless device 10used to make the transaction, such as “Samsung.” Entry 410 stores themodel of the wireless device 10 used to make the transaction, such as“Galaxy.” Entry 412 stores the mobile directory number (“MDN”), i.e.,the phone number, associated with the wireless device 10 used to makethe transaction, such as “123-456-7890.”

Entries 414-426 identify the transaction. Entry 414 stores the purchasetime and date of the transaction, such as “01/01/2012 8:15 AM.” Entry416 stores an identification number for the transaction, such as“A1234.” Entry 418 stores the order time and date of the transaction,such as “01/01/2012 9:55 AM.” In some implementations, the transactioncan be a purchase that is effective immediately and, thus, the purchasedate and time and the order date and time can be the same. In otherimplementations, the transaction can be a purchase to be available inthe future and, thus, the purchase date and time can be before the orderdate and time.

Entry 420 stores an identifier of the product purchased in thetransaction, such as “123XYZ456.” Entry 422 stores the name of theproduct purchased in the transaction, such as “60 Minute Package.” Entry424 stores the description of the product purchased in the transaction,such as “Voice Time of 60 Minutes.” Entry 426 stores the type of theproduct purchased in the transaction, such as “Voice.” In someimplementations, the type of product entry 426 can be one of the typesof wireless services, such as voice, SMS messaging, and data. However,the type of product entry 426 can be any type of product, such as, forexample, a wireless device and/or an accessory for a wireless device.

Entries 428-430 identify the vendor that was used to make thetransaction. Entry 428 stores the vendor name used to make thetransaction, such as “Tracfone.” In some implementations, the vendor canbe the MVNO that sells a wireless device and/or wireless service to thesubscriber. In other implementations, the vendor can be a third partythat resells the MVNO's products and/or services. Entry 430 stores anidentifier of the vendor used to make the transaction, such as “A1.”

Entries 432-450 store billing information for the transaction. Entry 432stores the retail price of the product purchased in the transaction,such as “$19.99.” Entry 434 stores the purchase price of the productpurchased in the transaction, such as “$14.99.” In some implementations,the purchase price entry 434 can be the same as the retail price entry432. In other implementations, the purchase price entry 434 can be lowerthan the retail price entry 432 reflecting a discount for the purchase.Entry 436 stores the payment type of the transaction, such as “creditcard.” Other payment types, including cash, check, and the like, canalso be stored in the payment type entry 436. Entry 438 stores thebilling date and time of the transaction, such as “01/01/2012 10:00 AM.”Entry 440 stores the billing city of the transaction, such as“Washington.” Entry 442 stores the billing state of the transaction,such as “DC.” Entry 444 stores the billing zip code of the transaction,such as “20036.” The billing city entry 440, billing state entry 442,and billing zip code entry 444 can store information regarding thebilling address of the wireless subscriber making the purchase.

Entry 446 stores the credit card type used to pay for the transaction,such as “XYZ Card.” Entry 448 stores an identifier for the credit cardrequest used to pay for the transaction, such as “1234-5678-9012-3456.”Entry 450 stores an identifier for the merchant processing the paymentof the transaction, such as “ProcessingCenter.” Although example datafor the entries 406-450 are illustrated in FIG. 4, any alphanumeric datacan be stored in the entries 406-450 depending on the transaction.

FIGS. 5a-5d illustrate exemplary graphical user interfaces (“GUIs”) ofthe wireless account management application 312. The wireless accountmanagement application 312 can also include other GUIs that are notillustrated. The user, i.e., the wireless subscriber, of the wirelessdevice 10 can select to run the wireless account management application312 by selecting an icon associated with the wireless account managementapplication 312. For example, the wireless subscriber can touch the iconassociated with the wireless account management application 312 on ahomepage displayed on the display 12 of the wireless device 10.

In some implementations, before allowing the subscriber to accesshis/her account information, the wireless account management application312 can require that the subscriber enter authentication credentials.For example, the subscriber can be required to enter a username andpassword combination, a personal identification number (“PIN”),biometric information, and the like. In a particular example, thewireless account management application 312 can automatically recall theusername of the subscriber and, thus, the subscriber can only berequired to enter a password. In some implementations, the subscribercan be required to enter the authentication credentials only the firsttime he/she accesses the wireless account management application 312.The authentication credentials may then be saved for the subscriber toenable the subscriber to view the welcome page GUI 500 of the wirelessaccount management application 312 after selecting the icon associatedwith the wireless account management application 312 without enteringany authentication credentials.

Moreover, although objects 502-568 are illustrated in the GUIs 500-560of FIGS. 5a-5d , one or more of the objects 502-568 can be removed fromthe GUIs and/or one or more objects that are not illustrated can beadded to the GUIs. For example, the welcome page GUI 500 may notillustrate an advertisement 526. In addition, although objects 502-568are illustrated according to a particular layout in the GUIs 500-560,the layout of the objects 502-568 can be changed to any other layout.For example, the banner 502 can be moved to directly above theadvertisement 526 at the bottom of the welcome page GUI 500. Finally,although the objects 502-568 are shown having various shapes and sizes,the size and/or shape of one or more of the objects 502-568 can bechanged. For example, the MVNO logo 504 can be made to encompass theentire welcome page GUI 500 as a watermark image in the background ofthe GUI.

Referring to FIG. 5a , the welcome page GUI 500 is illustrated. Thebanner 502, MVNO logo 504, wireless subscriber greeting 506, phonenumber associated with the wireless device 507, and service end date 508can be displayed at the top of the welcome page GUI 500. In someimplementations, the objects 502-508 can be displayed in every GUI ofthe wireless account management application 312. For example, theobjects 502-508 can be displayed at the top of every GUI of the wirelessaccount management application 312, as illustrated in FIGS. 5a -5 d.

The wireless account management application 312 can retrieve some or allof the information to display the objects 502-508 from the wirelesssubscriber service system 320 of the MVNO cloud 306. For example, thewireless account management application 312 can retrieve the banner 502and the service end date 508 from the wireless subscriber service system320, while retrieving the MVNO logo 504, wireless subscriber greeting506, and phone number 507 from a memory on the wireless device 10.

The banner 502 displays MVNO company information, such as, for example,company history, company milestones, marketing campaigns, and productinformation. For example, if the MVNO has decided to offer a discount onwireless products and/or services for a particular time period,information regarding this promotion can be displayed in the banner 502during that particular time period. In another example, the MVNO candisplay a company milestone, such as signing up its hundred millionthsubscriber in the banner 502. As such, the banner 502 can change everytime the subscriber accesses the wireless account management application312, at predetermined time periods according to the promotions of theMVNO, after a predetermined number of impressions, or the like. Thebanner 502 can include any combination of images and/or text.

The MVNO logo 504 is an image or text object of the logo of the MVNO.The wireless subscriber greeting 506 displays a salutation and the nameof the wireless subscriber. For example, the wireless subscribergreeting 506 can display “Hi Bob,” “Welcome Bob,” or the like. In someimplementations, the wireless subscriber greeting 506 can changedepending on date and time. For example, before noon, the wirelesssubscriber greeting 506 can display “Good morning Bob” and after noon,the wireless subscriber greeting 506 can display “Good afternoon Bob.”The phone number 507 is the phone number for the wireless subscriberthat is associated with the wireless device 10. In some implementations,if the wireless subscriber uses the wireless device 10 in differentgeographical boundaries, such as different countries, the phone number507 displayed can change depending on the geographical location.

The service end date 508 displays the final date that the subscriber haswireless service access with the MVNO according to his/her currentwireless service contract. If the subscriber purchases another wirelessservice contract or extends his/her current wireless service contract,the service end date 508 may change to a later date. In someimplementations, if a low number, i.e., less than a predeterminednumber, of days remain on the current wireless contract of thesubscriber, an alert can be forwarded to subscriber from the MVNO. Forexample, a call from a customer service representative can be placed tothe wireless device 10, an SMS message can be sent to the wirelessdevice 10, an alert can be displayed the next time the subscriber runsthe wireless account management application 312, and the like.

The find retailer button 522 is selectable by the subscriber and enablesthe subscriber to find retailers that are associated with the MVNO. Forexample, after selecting the find retailer button 522, the subscribermay view a GUI including a map identifying the physical locations, i.e.,stores, that sell the MVNO's wireless products and services close to,i.e., within a predetermined distance of, the physical location of thewireless device. In another example, after selecting the find retailerbutton 522, the subscriber can be linked to a webpage including alisting of physical locations that sell the MVNO's wireless products andservices close to the physical location of the wireless device. In someimplementations, directions to one or more of the physical locations canbe provided to the subscriber based on the physical location of thewireless device 10 and the address of a store of interest to thesubscriber.

The recommend us button 524 is selectable by the subscriber and enablesthe subscriber to recommend the MVNO's product and services. Forexample, after selecting the recommend us button 524, a prefilled SMSmessage or prefilled email can be presented to the subscriber to forwardto one or more contacts. In another example, after selecting therecommend us button 524, the subscriber can be linked to the webpage ofthe MVNO or a social media webpage associated with the MVNO. Thesubscriber can then signify or “like” the webpage. In yet anotherexample, after selecting the recommend us button 524, the subscriber mayautomatically signify or “like” a webpage associated with the MVNO.

The advertisement 526 displays an advertisement for the MVNO or a thirdparty. The advertisement 526 can be displayed on none, some, or all ofthe GUIs of the wireless account management application 312. Thewireless account management application 312 retrieves the advertisementfrom the wireless subscriber service system 320 or from a third partyadvertisement system. The advertisement 526 can be selectable, such thatselection of the advertisement directs the subscriber to, for example, aparticular webpage, a particular phone number, or the like. Theadvertisement 526 can include any combination of images and/or text.

In some implementations, the advertisement 526 displays an advertisementthat is selected for a particular subscriber. The advertisement 526 canbe selected based on the account information of the subscriber stored inthe wireless subscriber service system 320 and/or other informationstored on the wireless device 10. For example, the advertisement 526 canbe selected based on the browser history, the other stored mobileapplications, and other subscriber specific information on the wirelessdevice 10.

The buttons 510-520 enable a wireless subscriber to access various GUIsof the wireless account management application 312. The buttons 510-520may be static or may be dynamic and retrieved from the wirelesssubscriber service system 320. The account management button 510 allowsthe wireless subscriber to view and/or change account information. Thesubscriber can select the account management button 510 to access theaccount management GUI 530 of FIG. 5b by, for example, touching theaccount management button 510. The subscriber may be required to enteraccount information, such as a name, identification number, shippingaddress, billing address, form of payment, or the like, the first timethe subscriber uses the wireless account management application 312. Thesubscriber can then change any of his/her account information in theaccount management GUI 530. In some implementations, the subscriber canalso view wireless service usage in real-time or for predetermined timeperiods by selecting the account management button 510, as explained ingreater detail with regard to the account management GUI 530.

The usage purchase button 512 allows the wireless subscriber to purchasepredetermined units of usage for one or more wireless services. Forexample, the subscriber can purchase 60 minutes of voice usage or 250SMS messages. In another example, the subscriber can purchase a bundleof 60 minutes of voice usage, 250 SMS messages, and 2 GB of data usage.The subscriber can select the usage purchase button 512 to access theusage purchase GUI 550 of FIG. 5c by, for example, touching the usagepurchase button 512. For security reasons, the subscriber may berequired to enter authentication credentials every time the subscriberpurchases wireless usage using the wireless account managementapplication 312.

The monthly wireless service plan button 514 allows the subscriber topurchase a monthly wireless service plan that includes a predeterminednumber of units of one or more wireless services each month. Theinformation regarding the current monthly service plans available to thesubscriber by the MVNO can be retrieved from the wireless subscriberservice system 320. In addition, the subscriber can cancel a monthlywireless service plan or switch from one monthly wireless service planto another. For example, the subscriber may wish to increase or decreasehis/her monthly wireless service usage. For security reasons, thesubscriber may be required to enter authentication credentials everytime the subscriber purchases or changes his/her monthly wirelessservice plan using the wireless account management application 312.

Following selection of the monthly wireless service plan button 514, amonthly wireless service plan GUI can be illustrated to the subscriber.For example, the monthly wireless service plan GUI can includeindividual selectable buttons for each monthly wireless service planavailable to the subscriber. Other information, such as the number ofunits of wireless services credited every month, the number of months ofservice, whether unused units of wireless service roll over, the pricesof the monthly wireless service plans, and the like, can also bedisplayed. Different monthly wireless service plans can providedifferent levels of usage of wireless services at different prices. Forexample, one monthly wireless service plan can provide 300 minutes ofvoice usage over a three month period, while another monthly wirelessservice plan can provide 100 minutes of voice usage, 250 SMS messages,and 1 GB of data usage over a one month period.

Selection of a particular monthly wireless service plan may direct thesubscriber to a payment GUI for payment of the cost of the monthlywireless service plan. The payment GUI can enable the subscriber to paywith a stored credit card, enter a new credit card, pay with a prepaidcard on reserve as explained in greater detail with reference to button552, and/or enroll in automatic monthly payments for the monthlywireless service plan. Following payment of the cost of the monthlywireless service plan, the data for the transaction may be sent to thewireless subscriber service system 320 for creating a new data field inthe account information database 322. In addition, a transaction summaryGUI informing the subscriber that the transaction was successful may bedisplayed.

The application store button 516 allows the subscriber to purchaseand/or download applications for the wireless device 10. The applicationcan be specific to the operating system of the wireless device 10. Theapplications available to the subscriber can be retrieved from thewireless subscriber service system 320 or from a third party applicationsystem. The applications can include applications from the MVNO and/or athird party. Following download, the applications can be stored in thememory 20 of the wireless device and processed by the processor 18 ofthe wireless device.

The international wireless service button 518 allows the subscriber topurchase or receive information regarding usage of internationalwireless service. For example, following selection of the internationalwireless service button 518, an international wireless service GUI canbe displayed to the subscriber. The international wireless service GUIcan include individual selectable buttons for each internationalwireless service option available to the subscriber. For example, thesubscriber can purchase particular units of one or more internationalwireless services over a predetermined time period for a predeterminedprice. In another example, direct inward dialing (“DID”) numbers can bedisplayed to the subscriber in the international wireless service GUI.In some implementations, the information displayed in the internationalwireless service GUI can be retrieved from the wireless subscriberservice system 320. Selection of a particular international wirelessservice option may direct the subscriber to the payment GUI for paymentof the cost of the monthly wireless service plan.

The customer service button 520 allows the subscriber to access customerservice of the MVNO. Following selection of the customer service button520, a customer service GUI 560 is displayed to the subscriber, asexplained in greater detail with regard to FIG. 5 d.

Referring to FIG. 5b , following selection of the account managementbutton 510, the account management GUI 530 may be displayed. The accountmanagement GUI 530 can display usage of wireless services for thesubscriber, such as voice usage 532, SMS messaging usage 534, and datausage 536. The usage of the wireless services can be current to themoment the subscriber selects the account management button 510, i.e.,real-time. Alternatively, the usage of the wireless services can be forprior predetermined time periods, such as prior months and/or billingcycles. The other account information for the subscriber can bedisplayed in response to selection of the account information button537. The subscriber can view and/or update his/her account informationon an account information GUI.

In some implementations, the account management GUI 530 can displayusage of wireless services remaining for the subscriber's wirelessservice account. For example, the number of voice minutes remaining, thenumber of SMS messages remaining, and the amount of data transferremaining can be displayed. In some implementations, the usage and/orremaining usage of wireless services for the subscriber can be retrievedby the wireless account management application 312 from the trackingmodule 310 of the wireless device 10. In other implementations, theusage of wireless services for the subscriber can be retrieved by thewireless account management application 312 from the tracking module 310of the wireless device 10 while the remaining usage of wireless servicesfor the subscriber can be retrieved from the wireless subscriber servicesystem 320. In yet other implementations, both the usage and remainingusage of wireless services for the subscriber can be retrieved by thewireless account management application 312 from the wireless subscriberservice system 320.

In some implementations, the option to purchase additional usage ofindividual wireless services can also be displayed on the accountmanagement GUI 530. Button 538 is selectable to enable the purchase ofadditional voice minutes, button 540 is selectable to enable thepurchase of additional SMS messages, and button 542 is selectable toenable the purchase of additional data usage. Selection of one of thebuttons 538-542 by the subscriber can result in display of a purchasingGUI for that particular wireless service. For example, if the subscriberselects button 532, a voice service purchasing GUI can be displayed thatincludes individual selectable buttons for different units of voiceservice. Similarly, selection of button 534 triggers display of an SMSmessage purchasing GUI and selection of button 536 triggers display of adata purchasing GUI.

While in some implementations, buttons 538-542 can always be displayedon the account management GUI 530, in other implementations, buttons538-542 can only be displayed if the subscriber has a low number, i.e.,below a predetermined number, of units for that wireless serviceremaining in his/her account. For example, if the subscriber has lessthan one hundred voice minutes remaining in his/her account, button 538can be displayed to enable the subscriber to purchase additionalminutes. However, in such an example, buttons 540 and 542 may not bedisplayed because the subscriber has more than the predetermined unitsof usage of SMS messages and data transfer remaining in his/her account.The predetermined number of units remaining that triggers display ofbuttons 538-542 can differ for each of the different wireless services.

Referring to FIG. 5c , following selection of the usage purchase button512, the usage purchase GUI 550 is displayed. The usage purchase GUI 550includes the buttons 538-542 for the purchase of units of voice service,SMS messaging server, and data service. In addition, button 551 isselectable to enable purchase of a bundle of units of wireless services.For example, if the subscriber selects button 551, a wireless servicebundle purchasing GUI can be displayed that includes individualselectable buttons for different bundles of units of wireless services.

Button 552 is selectable to add the units of wireless service or amonetary amount from a prepaid card to the subscriber's account.Following selection of the button 552, a prepaid card reserve GUI isdisplayed to the subscriber. The subscriber can enter an identifier,such as a serial number of the prepaid card in the prepaid card reserveGUI. The identifier of the prepaid card is then sent from the wirelessdevice 10 to the wireless subscriber service system 320. The wirelesssubscriber service system 320 determines either a number of units ofwireless service or a monetary value associated with the prepaid card.In some implementations, that number of units of the wireless service ormonetary value is immediately added to the subscriber's wireless serviceaccount. In other implementations, that number of units of the wirelessservice or monetary value is reserved and not added to the subscriber'swireless service account, so that the subscriber can add the units ofthe wireless service or monetary value at a later time.

Button 554 is selectable to setup automatic refill of the units ofwireless service or a monetary amount to the subscriber's account.Following selection of the button 554, an automatic refill GUI isdisplayed to the subscriber. The subscriber can select for the MVNO toautomatically, i.e., without user augmentation or interaction, purchaseadditional usage or deposit additional money into the subscriber'saccount following a trigger event. The trigger event can be that theremaining usage of one or more wireless services or monetary value inthe subscriber's account is below a predetermined threshold. The triggerevent can be the start of a predetermined time period, such as thebeginning of the next month and/or new billing cycle. The trigger can bea predetermined time before the end service date of the wireless servicecontract. Payment for the automatic purchase or deposit of money can befrom a stored credit card in the subscriber's account, withdrawal from astored bank account in the subscriber's account, a prepaid card onreserve in the subscriber's account, and the like.

Referring to FIG. 5d , following selection of the customer servicebutton 520, the customer service GUI 560 is displayed. The customerservice GUI 560 includes button 562 that is selectable to displayfrequently asked questions (“FAQs”) and button 564 that is selectable todisplay contact information for the MVNO such as, for example, a webaddress, a physical address, an email address, one or more phonenumbers, and the like. Button 566 is selectable to enable the wirelessdevice 10 to call a customer service phone number for the MVNO withoutthe need for the subscriber to enter the customer service phone number.Button 567 is selectable to enable the subscriber to chat in real-timewith customer service representative of the MVNO. In someimplementations, if a customer service representative is not availableto chat, the color of the button 567 can be change and/or the button 567can be made unselectable. Button 568 is selectable to display the termsand conditions of the MVNO. The information displayed to the subscriberin response to selection of any one of the buttons 562-568 can beretrieved from the wireless subscriber service system 320.

FIG. 6 illustrates a flowchart showing an exemplary process fordisplaying wireless service usage information and account information ona wireless device. One or more steps in the process 600 can be carriedout by, for example, an electronic system such as the wireless device10, the wireless subscriber service system 320 of the MVNO cloud 306,and a third party system. Following selection of the icon associatedwith the wireless account management application 312, the wirelessaccount management application 312 can send an identifier of thewireless subscriber and/or wireless device 10 to the tracking modules308 and 310 as well as the wireless subscriber service system 320 toreceive the wireless service usage information and the accountinformation.

Initially, wireless service usage information is received from thewireless device 10 (step 602). The wireless account managementapplication 312 receives the wireless service usage information from thetracking module 310 of the wireless device 10. In some implementations,the wireless service usage information can be received followingselection of the icon associated with the wireless account managementapplication 312 while in other implementations, the wireless serviceusage information can be received following selection of the accountmanagement button 510.

The wireless service usage information includes one or more of thenumber of voice calls, the number of free voice minutes used, the numberof metered voice minutes used, the total number of voice minutes used,the number of free SMS messages sent and/or received, the number ofmetered SMS messages sent and/or received, the total number of SMSmessages sent and/or received, the free amount of data uploaded and/ordownloaded, the metered amount of data uploaded and/or downloaded, andthe total amount of data uploaded and/or downloaded. The receivedwireless service usage information can be usage from the start of arelationship between a wireless subscriber and the MVNO or forpredefined time periods. For example, the wireless service usageinformation can be received for the current billing cycle.

In some implementations, other wireless service usage information canoptionally be received from the MVNO cloud 306 (step 604). Inparticular, the wireless account management application 312 can receivethe other wireless service usage information from the tracking module308 of the MVNO cloud 306. In some implementations, the other wirelessservice usage information can be received from the tracking module 308at the same time that the wireless service usage information is receivedfrom the tracking module 310 while in other implementations, the otherwireless service usage information can be received from the trackingmodule 308 following reception of the wireless service usage informationfrom the tracking module 310.

In some implementations, the other wireless service usage informationcan be wireless service usage information that is not stored on thetracking module 310 of the wireless device 10. For example, the trackingmodule 310 may store wireless service usage information for a currentbilling cycle and the subscriber may request to view cumulative wirelessservice usage information for the duration of the relationship betweenthe subscriber and the MVNO. The wireless account management application312 may then receive wireless service usage information for the currentbilling cycle from the tracking module 310 and other wireless serviceusage information for previous billing cycles from the tracking module308 and sum the usages together.

In another example, the tracking module 310 may store only voice usageinformation and the subscriber may request to view usage of voice, SMSmessaging, and data services. The wireless account managementapplication 312 may then receive voice usage information from thetracking module 310 and SMS messaging and data usage from the trackingmodule 308.

In yet another example, the wireless account management application 312may include a usage checking feature that confirms the wireless serviceusage. In particular, wireless account management application 312receives wireless service usage information from the tracking module 310for a particular time period and the other wireless service usageinformation from the tracking module 308 for the same time period andcompares the usages of the wireless services. Only if the usages areconsistent may the wireless account management application 312 enabledisplay of the wireless service usage information.

Account information is also received from the MVNO cloud 306 (step 606).In particular, information regarding the management of the wirelesssubscriber's account and/or wireless service purchase information isreceived by the wireless account management application 312 from thewireless subscriber service system 320. The account information caninclude any information necessary to perform the functions of thewireless account management application 312 and/or displayed to thesubscriber in the wireless account management application 312.

In some implementations, for example, the account information caninclude one or more of the banner 502, subscriber name displayed in thewireless subscriber greeting 506, and the service end date 508 displayedin the welcome page GUI 500. The account information can include theaccount information displayed to the subscriber in response to selectionof the account information button 537, such as the information stored inthe service account information database structure 400. The accountinformation can include one or more of the options to purchaseadditional usage of individual wireless services available to thesubscriber by the selection of buttons 538-542. The account informationcan also include one or more of the bundles of units of wirelessavailable to the subscriber, the addition of a prepaid card to thesubscriber's account, information regarding any prepaid cards that arealready reserved in the subscriber's account, and the indication ofwhether the subscriber's account includes automatic refill. In addition,the account information can also include customer service informationthat is displayed in the customer service GUI 560, such as one or moreof FAQs, contact information for the MVNO, customer service phonenumbers, IP address for chatting with a customer service representativeof the MVNO.

The wireless account management application 312 then enablespresentation of the wireless service usage information and the accountinformation on the wireless device (step 608). In particular, thewireless account management application 312 configures one or more GUIs,such as GUIs 500-560 for display on the display 12 of the wirelessdevice 10.

For example, to configure the account management GUI 530, the wirelessaccount management application 312 receives the wireless service usageinformation from the tracking module 310 for display in objects 532-536and receives the account information from the wireless subscriberservice system 320 for configuring objects 537-542. The configuredaccount management GUI 530 is then sent to the display 12.

It is to be understood the implementations are not limited to particularsystems or processes described which may, of course, vary. It is also tobe understood that the terminology used herein is for the purpose ofdescribing particular implementations only, and is not intended to belimiting. As used in this specification, the singular forms “a,” “an,”and “the” include plural referents unless the content clearly indicatesotherwise. Thus, for example, reference to “a wireless device 10”includes two or more wireless devices.

Reference to “one implementation,” “some implementations,” “otherimplementations,” or “one or more implementations” means that aparticular feature, structure, or characteristic described in connectionwith the implementation is included in at least one implementation butnot necessarily in the same implementation or separate implementationsthat are mutually exclusive. Moreover, various features may be exhibitedby some implementations and not by other implementations. Similarly,various requirements are described that may be requirements for someimplementations but not other implementations.

A number of implementations have been described. Nevertheless, it willbe understood that various modifications may be made without departingfrom the spirit and scope of the claims. For example, the wirelessdevice 10 may not utilize a UICC or SIM card 22. The wireless device 10may operate using any mobile operating system. The internally storedrules of operation of the wireless device 10 may be changed togetherwith other wireless devices via a broadcast message received from theMVNO.

Although for the sake of clarity and simplicity, exemplaryimplementations of the invention is described in terms of a wirelessdevice 10 used in a MVNO communications system, it should be understoodthat the invention is not limited to these exemplary implementations.Accordingly, other implementations are within the scope of thisapplication.

The invention may include communication channels that may be any type ofwired or wireless electronic communications network, such as, e.g., awired/wireless local area network (LAN), a wired/wireless personal areanetwork (PAN), a wired/wireless home area network (HAN), awired/wireless wide area network (WAN), a campus network, a metropolitannetwork, an enterprise private network, a virtual private network (VPN),an internetwork, a backbone network (BBN), a global area network (GAN),the Internet, an intranet, an extranet, an overlay network, a cellulartelephone network, a Personal Communications Service (PCS), using knownprotocols such as the Global System for Mobile Communications (GSM),CDMA (Code-Division Multiple Access), W-CDMA (Wideband Code-DivisionMultiple Access), Wireless Fidelity (Wi-Fi), Bluetooth, and/or the like,and/or a combination of two or more thereof.

The invention may be implemented in any type of computing devices, suchas, e.g., a desktop computer, personal computer, a laptop/mobilecomputer, a personal data assistant (PDA), a mobile phone, a tabletcomputer, cloud computing device, and the like, with wired/wirelesscommunications capabilities via the communication channels.

In an embodiment, the invention may be implemented in any type of mobilesmartphones that are operated by any type of advanced mobile dataprocessing and communication operating system, such as, e.g., an Apple™iOS™ operating system, a Google™ Android™ operating system, a RIM™Blackberry™ operating system, a Nokia™ Symbian™ operating system, aMicrosoft™ Windows Mobile™ operating system, a Microsoft™ Windows Phone™operating system, a Linux™ operating system or the like.

Further in accordance with various embodiments of the invention, themethods described herein are intended for operation with dedicatedhardware implementations including, but not limited to, PCs, PDAs,semiconductors, application specific integrated circuits (ASIC),programmable logic arrays, cloud computing devices, and other hardwaredevices constructed to implement the methods described herein.

It should also be noted that the software implementations of theinvention as described herein are optionally stored on a tangiblestorage medium, such as: a magnetic medium such as a disk or tape; amagneto-optical or optical medium such as a disk; or a solid statemedium such as a memory card or other package that houses one or moreread-only (non-volatile) memories, random access memories, or otherre-writable (volatile) memories. A digital file attachment to email orother self-contained information archive or set of archives isconsidered a distribution medium equivalent to a tangible storagemedium. Accordingly, the invention is considered to include a tangiblestorage medium or distribution medium, as listed herein and includingart-recognized equivalents and successor media, in which the softwareimplementations herein are stored.

The many features and advantages of the invention are apparent from thedetailed specification, and, thus, it is intended by the appended claimsto cover all such features and advantages of the invention which fallwithin the true spirit and scope of the invention. Further, sincenumerous modifications and variations will readily occur to thoseskilled in the art, it is not desired to limit the invention to theexact construction and operation illustrated and described, and,accordingly, all suitable modifications and equivalents may be resortedto that fall within the scope of the invention.

What is claimed is:
 1. A method for displaying wireless service usageinformation and account information using an account managementapplication operating on a wireless device, comprising: receiving, atthe account management application operating on the wireless device andfrom a tracking module implemented by a wireless service provider,wireless service usage information for a wireless subscriber associatedwith the wireless device, the wireless service usage informationincluding one or more units of wireless services that the wirelesssubscriber has used, the wireless service provider being different fromthe wireless device and a wireless network that provides wirelessservice to the wireless device; receiving, at the account managementapplication operating on the wireless device and from the wirelessservice provider over the wireless network, account informationassociated with the wireless subscriber associated with the wirelessdevice that is stored in an account information database implemented bythe wireless service provider; receiving, at the account managementapplication operating on the wireless device and from the trackingmodule implemented by the wireless service provider and from thewireless service provider over the wireless network, other wirelessservice usage information, the other wireless service usage informationincluding one or more units of wireless services that the wirelesssubscriber has used; enabling presentation, on a display of the wirelessdevice, of the account management application including the wirelessservice usage information and the account information for the wirelesssubscriber associated with the wireless device; receiving, at theaccount management application operating on the wireless device and fromthe wireless subscriber associated with the wireless device, anidentifier of a prepaid card; forwarding, from the account managementapplication operating on the wireless device and to a service providerover the wireless network, the identifier of the prepaid card;determining, at the service provider, a number of units of wirelessservice or a monetary value associated with the prepaid card; anddepositing, at the service provider, the number of units of wirelessservice or the monetary value associated with the prepaid card, in anaccount associated with the wireless subscriber.
 2. The method of claim1, further comprising receiving, at the account management applicationoperating on the wireless device, an indication that the wirelesssubscriber has selected to view the wireless service usage informationfor the wireless subscriber.
 3. The method of claim 2, wherein receivingthe indication that the wireless subscriber would like to view thewireless service usage information for the wireless subscriber comprisesreceiving the indication that the wireless subscriber has selected abutton in the account management application.
 4. The method of claim 1,further comprising storing, on a memory of the wireless device, theaccount information associated with the wireless subscriber.
 5. Themethod of claim 1, further comprising receiving, at the accountmanagement application operating on the wireless device, advertisementinformation selected for the wireless subscriber according to theaccount information associated with the wireless subscriber.
 6. Themethod of claim 1, wherein the enabling presentation of the accountmanagement application including the wireless service usage informationand the account information for the wireless subscriber associated withthe wireless device comprises the enabling presentation of the accountmanagement application including the wireless service usage information,the other wireless service usage information, and the accountinformation for the wireless subscriber associated with the wirelessdevice.
 7. The method of claim 1, wherein the other wireless serviceusage information comprises wireless service usage information that isnot included in the tracking module.
 8. The method of claim 1, wherein:the wireless service usage information includes one or more units ofwireless services that the wireless subscriber has used over a firsttime period, and the other wireless service usage information includesone or more units of wireless services that the wireless subscriber hasused over a second time period that is before the first time period. 9.The method of claim 1, wherein: the wireless service usage informationincludes one or more units of a first type of wireless service that thewireless subscriber has used, and the other wireless service usageinformation includes one or more units of a second type of wirelessservice that the wireless subscriber has used, the second type ofwireless service being different from the first type of wirelessservice.
 10. The method of claim 1, wherein the account informationassociated with the wireless subscriber associated with the wirelessdevice comprises options to purchase additional usage of wirelessservices available to the wireless subscriber.
 11. The method of claim10, wherein the options to purchase additional usage of wirelessservices available to the wireless subscriber comprise options topurchase one or more of voice minutes, Short Message Service messages,and data amount.
 12. The method of claim 10, wherein the enablingpresentation of the account management application including thewireless service usage information and the account information for thewireless subscriber associated with the wireless device comprises:determining that the wireless service usage information is below apredetermined threshold; and enabling presentation, in response to thedetermination that the wireless service usage information is below thepredetermined threshold, of the options to purchase additional usage ofwireless services available to the wireless subscriber.
 13. The methodof claim 1, wherein the wireless services comprise voice service, ShortMessage Service messaging service, and data service.
 14. The method ofclaim 1, wherein the account information associated with the wirelesssubscriber associated with the wireless device comprises a service enddate for the wireless subscriber.
 15. The method of claim 1, wherein theaccount information comprises an identifier of the wireless device, anidentifier of a transaction, an identifier of a vendor, and billinginformation.
 16. The method of claim 1, wherein the wireless deviceincludes a mobile phone.
 17. A wireless device comprising at least oneprocessor connected to at least one memory, wherein the at least oneprocessor is configured to: receive, at an account managementapplication operating on the wireless device and from a tracking moduleimplemented by a wireless service provider, wireless service usageinformation for a wireless subscriber associated with the wirelessdevice, the wireless service usage information including one or moreunits of wireless services that the wireless subscriber has used, thewireless service provider being different from the wireless device and awireless network that provides wireless service to the wireless device;receive, at the account management application operating on the wirelessdevice and from a service provider over the wireless network, accountinformation associated with the wireless subscriber associated with thewireless device that is stored in an account information databaseimplemented by the wireless service provider; receive, at the accountmanagement application operating on the wireless device and from thetracking module implemented by the wireless service provider and fromthe wireless service provider over the wireless network, other wirelessservice usage information, the other wireless service usage informationincluding one or more units of wireless services that the wirelesssubscriber has used; enable presentation, on a display of the wirelessdevice, of the account management application including the wirelessservice usage information and account information for the wirelesssubscriber associated with the wireless device; receive, at the accountmanagement application operating on the wireless device and from thewireless subscriber associated with the wireless device, an identifierof a prepaid card; and forward, from the account management applicationoperating on the wireless device and to a service provider over thewireless network, the identifier of the prepaid card; wherein theservice provider determines a number of units of wireless service or amonetary value associated with the prepaid card; and wherein the serviceprovider deposits the number of units of wireless service or themonetary value associated with the prepaid card, in an accountassociated with the wireless subscriber.
 18. The wireless device ofclaim 17, wherein: the wireless service usage information includes oneor more units of wireless services that the wireless subscriber has usedover a first time period, and the other wireless service usageinformation includes one or more units of wireless services that thewireless subscriber has used over a second time period that is beforethe first time period.
 19. A memory storing a non-transitory computerprogram, the non-transitory computer program comprising one or more codesegments that, when executed, cause at least one processor to: receive,at an account management application operating on a wireless device andfrom a tracking module implemented by a wireless service provider,wireless service usage information for a wireless subscriber associatedwith the wireless device, the wireless service usage informationincluding one or more units of wireless services that the wirelesssubscriber has used, the wireless service provider being different fromthe wireless device and a wireless network that provides wirelessservice to the wireless device; receive, at the account managementapplication operating on the wireless device and from the wirelessservice provider over the wireless network, account informationassociated with the wireless subscriber associated with the wirelessdevice that is stored in an account information database implemented bythe wireless service provider; receive, at the account managementapplication operating on the wireless device and from the trackingmodule implemented by the wireless service provider and from thewireless service provider over the wireless network, other wirelessservice usage information, the other wireless service usage informationincluding one or more units of wireless services that the wirelesssubscriber has used; enable presentation, on a display of the wirelessdevice, of the account management application including the wirelessservice usage information and account information for the wirelesssubscriber associated with the wireless device; receive, at the accountmanagement application operating on the wireless device and from thewireless subscriber associated with the wireless device, an identifierof a prepaid card; and forward, from the account management applicationoperating on the wireless device and to a service provider over thewireless network, the identifier of the prepaid card; wherein theservice provider determines a number of units of wireless service or amonetary value associated with the prepaid card; and wherein the serviceprovider deposits the number of units of wireless service or themonetary value associated with the prepaid card, in an accountassociated with the wireless subscriber.